- 
                Notifications
    
You must be signed in to change notification settings  - Fork 29
 
feat(core/df-repr): better upper bound pruning to reduce plan space #265
Conversation
Signed-off-by: Alex Chi Z <[email protected]>
b3288bc    to
    7fef116      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]> tune plan space budget Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
7fef116    to
    b3cff3c      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
b3cff3c    to
    fc187cf      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
f225728    to
    cac5d3f      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
bf25604    to
    7f7c84d      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
7f7c84d    to
    5325531      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]> tune plan space budget Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
5325531    to
    e5f7c50      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed:
- cross join to inner join changes
 - main upper bound pruning logic in 
optimize_inputs_inner 
I need another look at task2.rs and potentially doc more aggressively like https://github.com/cmu-db/optd/pull/234. I actually like this version of the task graph a lot (no state machine logic).
Is there any other part of the logic I need pay special attention to?
| 
           I think part of this PR is tuning to ensure the plan is what we want (i.e., filter selectivity and behavior on reaching the budget). The tasks2.rs logic is also something that we should fully understand as we are going to bring more logic into it (phys prop, etc.)  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs to doc the task graph a little bit more but LGTM
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]> tune plan space budget Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
e5f7c50    to
    023d47e      
    Compare
  
    Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]> tune plan space budget Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Signed-off-by: Alex Chi Z <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.